OpenClaw 2026.6.1 Plugin Install Guide: What’s Bundled, What Lives in ClawHub, and How to Pin Compatible Integrations

As of June 7, 2026, the fastest way to break an OpenClaw rollout is to follow stale plugin advice. The npm registry entry for openclaw currently points latest to 2026.6.1 and beta to 2026.6.5-beta.2, while the current OpenClaw docs now split integrations across bundled plugins, ClawHub-distributed packages, and direct npm installs. That is a healthier model than the early-2026 “everything in core” sprawl, but only if operators know which source they are actually installing from.

If you need the broader ecosystem context first, read our earlier OpenClaw plugin ecosystem roundup. This post is narrower: what the current stable line appears to ship, what still lives outside core, and how to pin plugin compatibility without guessing.

1. The current stable line is newer than most public setup advice

The main operational fact today is simple: the stable npm line has moved to 2026.6.1. That matters because OpenClaw’s own plugin behavior is source-aware. The docs say community discovery now centers on ClawHub, bundled plugins can resolve from the packaged build instead of npm, and bare package names can behave differently depending on whether the plugin is bundled, official external, or just a normal npm package.

In plain English: “install the package” is no longer precise enough guidance for production teams. On current builds, you need to know whether you are intentionally using the bundled copy, following the official external package, or pinning an older compatible version for a controlled rollout.

2. What is bundled right now, and what still installs separately

Current docs show a mixed model rather than a one-size-fits-all plugin story:

  • Cloudflare AI Gateway is documented as included in OpenClaw.
  • Azure Speech is also documented as included in OpenClaw.
  • Microsoft Teams is documented as a bundled plugin in current OpenClaw releases, with direct npm install only for older or custom builds.
  • Slack is documented with install routes through npm and ClawHub.
  • Matrix is also documented with install routes through ClawHub and npm.

That split is the practical operator takeaway. If your team is standardizing on Slack or Matrix, you should treat those as explicitly managed external surfaces. If you are standardizing on Teams, Azure Speech, or Cloudflare AI Gateway on current packaged releases, the docs indicate that those capabilities already ride with the core build.

3. Why the split happened: lighter installs and a smaller default trust surface

The most useful technical explanation is OpenClaw’s own release performance sweep. That page documents the packaging cleanup that became visible in the May line, especially the 2026.5.12 plugin extraction milestone and the 2026.5.28 stable release. According to the sweep, v2026.5.12 was the visible point where Bedrock, Slack, OpenShell sandbox, Anthropic Vertex, Matrix, and WhatsApp moved out of the core dependency path.

The same sweep reports that v2026.5.28 cut fresh install size by 52.8% versus v2026.5.27, reduced unique dependency roots from 371 to 300, and improved cold agent-turn time by 14.5% compared with the previous stable release. The broader point is bigger than one benchmark table: OpenClaw is clearly trying to make the default install smaller, faster, and easier to trust, while pushing more optional integration weight to plugins.

That also lines up with our earlier install footprint analysis: production teams should now think in terms of a lean core plus a deliberately chosen plugin catalog, not a monolith.

4. Compatibility is not “whatever the latest package is”

The most important implementation detail lives in the plugin manifest reference. OpenClaw documents two separate compatibility checks for non-bundled plugins:

  • openclaw.install.minHostVersion for host-version gating during install and registry loading.
  • openclaw.compat.pluginApi for the plugin SDK or runtime API floor the package was built against.

The docs are explicit that the package version alone is not the real compatibility contract. For official external plugins, OpenClaw also documents exact npmSpec pinning, optional expectedIntegrity verification, and a preference for clawhubSpec when the plugin has moved to ClawHub.

That is the right mental model for serious operators: pin the source, pin the version when reproducibility matters, and treat compatibility as a declared policy field, not a vibe.

5. The safest install workflow on 2026.6.1

OpenClaw’s current plugin docs support a practical deployment pattern:

openclaw plugins install clawhub:<package>
openclaw plugins install npm:<package>
openclaw plugins inspect <plugin-id> --runtime --json
openclaw gateway restart

That matters because the docs also say:

  • ClawHub is the primary discovery surface for community plugins.
  • Bare package names can resolve to the bundled copy if the plugin is bundled.
  • For npm installs, an unpinned package can select the newest stable compatible package rather than blindly taking an incompatible latest build.
  • inspect --runtime is the clearest way to verify that the live Gateway actually loaded the plugin you think it did.

So the production-safe rule is: use explicit source prefixes when the source matters, pin exact versions when reproducibility matters, and verify the runtime instead of trusting the cold registry.

6. What teams should do next

If you run OpenClaw for one person, current docs make it much easier to stay on the bundled path and add only the integrations you need. If you run OpenClaw for a team, the packaging changes are a prompt to formalize an internal plugin policy: which integrations are allowed, which source each one comes from, what compatibility floor you accept, and which environments may install beta packages.

That policy becomes even more valuable if you are balancing Slack, Teams, and self-hosted gateway workflows across multiple operators. If you want help turning the current OpenClaw plugin model into a reproducible deployment baseline, ALL CLEAR DIGITAL can build the compatibility matrix, pin the approved plugin catalog, and design a managed rollout for your team’s real chat surfaces and agent workflows.

Sources: npm package metadata for openclaw, OpenClaw plugin docs, plugin manifest reference, release performance sweep, Cloudflare AI Gateway plugin, Azure Speech plugin, Slack plugin, Matrix plugin, and Microsoft Teams channel docs.